gDEBugger User Guide| gDEBugger User Guide |
The Process Events view displays events that occur during the debugged process execution.
The debugged process events are displayed as a list, ordered by the time in which they occurred.
The debugged process was created in the operating system.
The debugged process run was started.
A dynamic linked library was loaded and mapped into the debugged process address space.
A dynamic linked library was unmapped from the debugged process address space.
An OpenGL error occurred.
A debugged process thread threw an exception. During the search for structured exception handlers, either no handler was found or the exception was continued. The process is about to exit
A debugged process thread hit a breakpoint.
The debugged process sent a debug string to its debugger. This is usually done using the Win32 OutputDebugString function.
The debugged process was advanced to the next OpenGL function call using the Step button.
The debugged process execution was suspended using the Break button.
Selecting a list line presents the appropriate debugged process event detailed in the Properties view.
A foreign breakpoint is a breakpoint exception not initiated by gDEBugger. Such breakpoints are usually triggered by calling the Win32 DebugBreak function or calling the assembly command int 3 on Intel CPUs.